fix: allow use of built-in routing tables#804
Merged
richm merged 1 commit intolinux-system-roles:mainfrom Sep 4, 2025
Merged
Conversation
Cause: The user is trying to specify the routing table to use by the name of a built-in routing table defined in /usr/share/iproute2/rt_tables such as `main`. Consequence: The network role gives an error: "cannot find route table main in `/etc/iproute2/rt_tables` or `/etc/iproute2/rt_tables.d/`" The workaround is that the user must specify the table by number instead of name e.g `table: 254` instead of `table: main` Fix: Look for table mappings in /usr/share/iproute2/rt_tables as well as the other paths. Result: The user can use built-in route table names. Signed-off-by: Rich Megginson <rmeggins@redhat.com>
Reviewer's GuideExtend route table mapping to recognize built-in tables from /usr/share/iproute2/rt_tables and update tests to verify both built-in (‘main’) and custom named table functionality. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
Contributor
Author
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #804 +/- ##
==========================================
+ Coverage 43.11% 43.24% +0.12%
==========================================
Files 12 12
Lines 3124 3122 -2
==========================================
+ Hits 1347 1350 +3
+ Misses 1777 1772 -5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Contributor
Author
|
[citest] |
Contributor
Author
|
[citest_bad] |
1 similar comment
Contributor
Author
|
[citest_bad] |
Contributor
Author
|
[citest] |
Contributor
Author
|
cs9 failing - looks like the highavailability repo config is messed up again :-( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cause: The user is trying to specify the routing table to use by the name of
a built-in routing table defined in /usr/share/iproute2/rt_tables such as
main.Consequence: The network role gives an error:
"cannot find route table main in
/etc/iproute2/rt_tablesor/etc/iproute2/rt_tables.d/"The workaround is that the user must specify the table by number instead of name e.g
table: 254instead oftable: mainFix: Look for table mappings in /usr/share/iproute2/rt_tables as well as the other
paths.
Result: The user can use built-in route table names.
Signed-off-by: Rich Megginson rmeggins@redhat.com
Summary by Sourcery
Enable specifying built-in route tables by name by loading mappings from the system rt_tables file and validate the behavior with new tests
Bug Fixes:
Enhancements:
Tests: